chore(release): 0.7.0 - #51
Merged
Merged
Conversation
willytop8
marked this pull request as ready for review
August 2, 2026 21:52
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
0.7.0Why
PR #50 added public lifecycle-message options and observable status behavior, so
the compatibility policy calls for a minor release. The README clarification
prevents the historical v0.6.6 provider matrix from reading like the current
package version or a current feature state.
Verification
npm run release:check— passedstatus/audit reporting, host logging, privacy, persistence, and cleanup
Release artifact
After this PR merges, create annotated tag
v0.7.0at the merge commit and useonly the tarball produced by the tag-triggered Release Check for npm publication.